Note that this should be /acs/systems/list

@kainpets can you see why this is off in blueprint?

Sorry, but I forgot to trigger the automatic release of blueprint when I pushed the fix for this. I've manually released yesterday and this should be fixed with version 0.2.1

This file and the other REAMDE can serve as landing pages for each SDK. The content can either live here or we can just generate an index partial to include in the readme via a gitbook include.

@mastafit We can add something like this instead if we want build a more complicated template context

@razor-x Sure, just give me some requirements for this one, what exactly such function should do?

It depends on what context we need for the template. So if we write the handlebars template and only need endpoint, then we are done. But we may need to extend the context, add to it, or transform it, if endpoint is not enough or hard to use in the template.

Ideally, blueprint would already have what we need so element should be a good context for the template, but at this stage we are still learning what we need in context.

If this gets too complex, we can move logic into handlebars helpers or back into the blueprint.

For example, one thing we want to do is update URLs to be relative in GitBook, e.g., if a description contains a Markdown link to to https://docs.seam.co/latest/core-concepts/overview we really want this to link to ../core-concepts/overview or whatever the correct internal GitBook linking should be.

Another example is we want to generate links to other resources, e.g., The acs_system is... should might get transformed to The [acs_system](../acs_system) is...`.

We can implement those two things later, I'm just using them as an example. But either it would be handled inside setFileContext or in the template via a helper like {{ element.description | linkResources | relativeLinks }}.

This PR does not include registering handlebars helpers, but it should be simple to add that under src/lib.

Since we're passing the path to metadata.codeSampleDefinitions in src/metalsmith.ts:

  .use(
    metadata({
      codeSampleDefinitions: './data/code-sample-definitions',
    }),
  )

I suppose we need to read all the definitions from './data/code-sample-definitions' and pass them instead of the path itself because TypesModuleSchema expects codeSampleDefinitions: z.array(CodeSampleDefinitionSchema).default([]) according to the ongoing blueprint PR?

Yes, TypesModuleSchema has all definitions, and then creates and passes only the code samples specific to each endpoint.